Skip to main content

This is a new service – your feedback will help us to improve it.

Buckinghamshire Council

Tree preservation zone

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

The Bucks County Council (Amersham Rural District) Tree Preservation Order No 13 - 1957 [Not confir

reference
ZZZZDVESXE666
name
The Bucks County Council (Amersham Rural District) Tree Preservation Order No 13 - 1957 [Not confir
tree-preservation-order

undefined

TPO/1957/013
tree-preservation-zone-type
geometry
MULTIPOLYGON (((-0.670111 51.676565,-0.670135 51.676580,-0.670176 51.676587,-0.670195 51.676592,-0.670203 51.676597,-0.670204 51.676605,-0.670218 51.676654,-0.670231 51.676684,-0.670263 51.676737,-0.670270 51.676755,-0.670276 51.676782,-0.670281 51.676826,-0.670348 51.676828,-0.670573 51.676829,-0.670828 51.676829,-0.670970 51.676827,-0.671032 51.676825,-0.671561 51.676795,-0.671745 51.676782,-0.671818 51.676781,-0.671949 51.676787,-0.671984 51.676791,-0.672017 51.676798,-0.672072 51.676816,-0.672132 51.676840,-0.672473 51.676997,-0.672567 51.677039,-0.672610 51.677054,-0.673054 51.677132,-0.673194 51.677151,-0.673222 51.677150,-0.673266 51.677137,-0.673406 51.677073,-0.673532 51.677008,-0.673661 51.676931,-0.673748 51.676875,-0.673789 51.676842,-0.673907 51.676728,-0.673960 51.676672,-0.674043 51.676571,-0.674055 51.676553,-0.674127 51.676360,-0.674152 51.676307,-0.674176 51.676263,-0.674206 51.676217,-0.674365 51.675994,-0.674377 51.675970,-0.674478 51.675802,-0.674518 51.675737,-0.674547 51.675696,-0.674574 51.675652,-0.674703 51.675420,-0.674795 51.675236,-0.674827 51.675165,-0.674854 51.675096,-0.674875 51.675032,-0.674886 51.674989,-0.674893 51.674954,-0.674907 51.674851,-0.674912 51.674825,-0.674919 51.674801,-0.675007 51.674525,-0.675129 51.674188,-0.675138 51.674171,-0.675153 51.674150,-0.675165 51.674139,-0.675690 51.673571,-0.675565 51.673535,-0.675443 51.673532,-0.676374 51.672825,-0.676463 51.672740,-0.676577 51.672606,-0.676581 51.672586,-0.676594 51.672544,-0.676601 51.672498,-0.676631 51.672246,-0.676641 51.672104,-0.676640 51.672065,-0.676653 51.671992,-0.676696 51.671893,-0.676711 51.671851,-0.676723 51.671805,-0.676730 51.671767,-0.676735 51.671727,-0.676736 51.671700,-0.676745 51.671628,-0.676764 51.671530,-0.676776 51.671486,-0.676845 51.671253,-0.676935 51.671016,-0.677043 51.670364,-0.676429 51.670252,-0.676169 51.670212,-0.675868 51.670169,-0.675678 51.670146,-0.675625 51.670244,-0.675511 51.670473,-0.675498 51.670505,-0.675440 51.670626,-0.675364 51.670763,-0.675289 51.670867,-0.674991 51.671558,-0.674943 51.671687,-0.674731 51.672277,-0.674719 51.672297,-0.674499 51.672626,-0.674385 51.672794,-0.674192 51.673073,-0.674128 51.673154,-0.674054 51.673232,-0.673638 51.673612,-0.673252 51.673593,-0.672999 51.673739,-0.672912 51.673791,-0.672800 51.673863,-0.672780 51.673874,-0.672771 51.673881,-0.672759 51.673896,-0.672756 51.673904,-0.672632 51.674068,-0.672597 51.674121,-0.672562 51.674178,-0.672533 51.674238,-0.672495 51.674323,-0.672417 51.674511,-0.672375 51.674603,-0.672347 51.674655,-0.672286 51.674752,-0.672216 51.674817,-0.672149 51.674872,-0.671941 51.675033,-0.671840 51.675212,-0.671116 51.675531,-0.671067 51.675558,-0.671028 51.675582,-0.671032 51.675639,-0.671037 51.675678,-0.671058 51.675777,-0.671058 51.675795,-0.671066 51.675911,-0.670323 51.676074,-0.669863 51.676170,-0.669866 51.676187,-0.669881 51.676216,-0.669905 51.676252,-0.669929 51.676293,-0.669941 51.676329,-0.669951 51.676369,-0.669960 51.676385,-0.670002 51.676445,-0.670025 51.676475,-0.670052 51.676507,-0.670076 51.676532,-0.670111 51.676565)))
point
POINT (-0.673968 51.674176)
notes
entry-date
2010-02-18
start-date
2010-02-18
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Buckinghamshire Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL